Emit diagnostic warning for deprecated Azure Functions Proxies usage #11405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: brettsam <[email protected]>
Copilot
AI
changed the title
Copilot finished work on behalf of
brettsam
October 2, 2025 21:11
liliankasem
reviewed
Oct 2, 2025
| _scriptOptions = scriptOptions; | ||
| _environment = environment; | ||
| _logger = loggerFactory.CreateLogger(LogCategories.Startup); | ||
| if (_environment.IsProxiesEnabled()) |
There was a problem hiding this comment.
Are there other places in the host we do this check?
There was a problem hiding this comment.
The warning here will be emitted simply if proxies feature flag is enabled. We may need to only emit warning if there are actual files with proxies. Otherwise, customers might be confused why the warning is generated. If we do want the warning here we also should provide instructions to remove feature flag.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements a diagnostic warning event that alerts users when Azure Functions Proxies are enabled, informing them of the deprecation and upcoming end of community support.
Background
Azure Functions Proxies are officially deprecated, with community support ending on September 30, 2025 (official announcement). Despite this deprecation, a significant number of production applications still have proxies enabled and users need to be proactively notified.
Changes
Diagnostic Event Constants
Added new diagnostic event constant
AZFD0014inDiagnosticEventConstants.cswith a help link pointing to the official Azure deprecation announcement.ProxyFunctionProvider Enhancement
Modified the
ProxyFunctionProviderconstructor to emit a diagnostic warning event when proxies are enabled. The warning message includes:Test Coverage
Added a new unit test
ProxyFunctionProvider_WhenProxiesEnabled_EmitsDiagnosticWarningthat verifies:AZFD0014) is usedBehavior
When an Azure Functions host starts up with proxies enabled:
ProxyFunctionProviderconstructor detects proxies are enabledAZFD0014Impact
MissingFunctionsWorkerRuntime,WorkerRuntimeDoesNotMatchWithFunctionMetadata)Fixes #[issue number]
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
azfunc.pkgs.visualstudio.comdotnet build src/WebJobs.Script/WebJobs.Script.csproj --configuration Release(dns block)/home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)dotnet restore src/WebJobs.Script/WebJobs.Script.csproj(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.